Conferencing User

The Conferencing user panel allows you to import LDAP users to log into the Cisco Meeting Web App.

Creating user accounts requires:

• Defining the connection properties to connect to your Active Directory server. By default, LDAPS option is selected.
• Defining the search filter and field mapping values with which users are created on a Meeting Server. Installation Assistant has default values that works for most environments, but you have the option to override those defaults if necessary.

If you wish to create user accounts:

1. Fill in the LDAP Connection Settings fields with the values for connecting to your Active Directory controller. A Next button will be displayed once all required fields are completed.

   Details on each setting are provided in the following table:

   Table 16: Configuring the LDAP connection

   Field Name	Description	Inputs
   Server address	The network address of the LDAP server to connect to.	The FQDN or IP Address of your LDAP server
   Port	The TCP port on the LDAP server to connect to.	A valid port number. The default value is 636 for LDAPS and 389 for LDAP.
   Username	The username of the user that will connect to the LDAP server. This user only needs read rights to the directory.	The LDAP Distinguished Name (DN) or UPN of the user to authenticate with. This field cannot be left blank
   Password	The password of the user specified.	Password of the user. This field cannot be left blank.
   Search base	The location in the LDAP directory from where import search queries will start from. For assistance with this value, contact your Domain Administrator.	The LDAP Distinguished Name (DN) of the directory location where searches should start. This field cannot be left blank
   Assign PMP licenses to users	If enabled, imported users will be marked to be entitled to a PMP+ license. Do not enable if you have not purchased PMP+ licenses for all users being imported.	Enable to tag each imported user as having a PMP+ entitlement.
   Override default user filter and field mapping details	Installation Assistant uses a default LDAP Search Filter and user field mappings that should work for most environments. This option when enabled, offers you the ability to view and customize these settings to fit your environment.	Enable to view or customize the LDAP search filter, and or LDAP user field mappings.

2. Click Check LDAP Connection button to make sure LDAP connectivity is available.

   Note: On clicking Check LDAP Connection button if the connection check fails, an error message is displayed: LDAP Connection Failed.

3. Once LDAP connectivity is established successfully, the Next button is enabled. Click Next

Note: Ensure that all the details are entered to save your settings successfully. If you are modifying the default values, ensure to use valid LDAP expressions used for the mapping.

Error Scenarios

• If on clicking Check LDAP Connection button, connection check fails
  Solution: You must provide valid LDAP connection details.

Customizing the LDAP Search and user mappings

Installation Assistant uses a default LDAP Search Filter and user field mappings that should work for most environments. The default, filters on users that have an email address defined, a username, and will set their Meeting Server username to their meeting address.

Enabling the override option will display the individual configuration fields used for import and show the settings Installation Assistant is using by default. When Override default user filter and field mapping details is enabled, users have the ability to customize these values to fit their environment.

The user mapping expressions define how to set the properties of a user when importing them into Meeting Server. The expressions use variables along with static text so that a user’s properties in LDAP can be used when creating the user in Meeting Server. The use of LDAP properties is critical to ensure properties that are required to be unique per user (such as username or URI) are not duplicated. LDAP properties are referenced by their property name enclosed with the $ symbol. Example: The LDAP property ‘mail’ is referenced by $mail$ in the field mapping expressions.

Table 17: LDAP Import settings

Field Name	Description	Inputs
LDAP search filter	Defines the criteria of which LDAP users will be matched to be imported.	LDAP search string. Must use LDAP search syntax
Display name	The name shown for the user in directories and searches.	Mapping expression. Example: $cn$
User name	The username that the user will use to log into Cisco Meeting Web App. The resulting value must be unique across all users and spaces.	Mapping expression. Example: $sAMAccountName$@company.com This field cannot be blank and the result must be unique for each imported user
Space name	Label given to space automatically created for user. Leave blank if not creating spaces for imported users.	Mapping expression. Example: $cn$ Meeting space
Space URI	Left hand portion of URI for the space automatically created for the user. Result must be unique per user and not conflict with usernames or other spaces. Leave blank if not creating spaces for imported users..	Mapping expression. Example: $cn$.space
Space secondary URI	Left hand portion of a second URI for the space automatically created for the user. Result must be unique per user and not conflict with usernames or other spaces. Optional field. Leave blank if not creating spaces for imported users.	Mapping expression. Example: $cn$.room
Space call ID	Sets the call ID for the space automatically created for the user. Result must be unique across all spaces. Optional field, Cisco Meeting Server will assign IDs automatically if left blank. Leave blank if not creating spaces for imported users.	Mapping expression.
Authentication ID mapping	Mapping property assigned to the imported user. Used in smartcard login scenarios. Leave blank unless specifically deploying certificate based logins.	Mapping expression. Example: $userPrincipalName$

 

The Next button is enabled. Click Next and the login credential is created, saved and you are navigated to next panel based on your chosen deployment.

Note: Ensure that all the details are entered to save your settings successfully.

Error Scenarios:

An error message is displayed and the Next button is disabled in case of the following scenarios:

• If the entered server address detail is incorrect.
  
  Solution: You must provide a valid IP address/ FQDN.
• If the entered port number is incorrect.
  
  Solution: You must provide correct and only numeric values.